Home Accounting 1.0.0a4 Bug List and Status Sheet:
This documents the bugs found and their current resolution status.
User vs. Programmer terminology:
To the user Home Accounting manages data bases.
To the programmer Home Accounting manages documents.
The following terms are interchangeable:
User>>Data Base, Programmer>>Document
User>>Data Base Number, Programmer>>Session
User>>Current Data Base, Programmer>>Active Session
User>>Data Base Manager, Programmer>>Documents Manager
User>>Data Base Data, Programmer>>Document Manager
ABC's>>Current Session, Home Accounting>>Next Session Number
-------------------------------
01 January 1996, Compile 3, 1.0.0a4p3f1 (bug fix, enhancements)
01 November 1995, Compile 3, 1.0.0a4p3 (conversion to CPX 1.3)
12 October 1995, Compile 2, 1.0.0a4p2
22 August 1995, Compile 1, 1.0.0a4p1 (conversion to CPX 1.2.2)
-------------------------------
If you send me a bug report, please try to follow the format of this document. Please supply as much information as possible.
-------------------------------
Bug Priority:
0
Critical (resolved as quickly as possible).
A bug entry gets this priority for 1 of 2 reasons. A required function crashes the application or a required function is missing or not functioning.
1
Serious (resolved after resolution of priority 0 bugs).
Any function that should work but doesn't.
2
Annoyance (resolved in do time, depending on how busy I am and how difficult it is to fix).
All parties (users, testers and author) agree that something in the application should be implemented in a different way or a feature should be present.
3
Superficial (will be resolved before the next version release).
Not all parties (users, testers or author) agree on how something in the application should be implemented, function or that a feature should be present. This does not mean that someone is annoying the author.
4
Wish list (resolved a lot like priority 3, depending on demand or my desire for the feature).
-------------------------------
Bug Type:
Bug
The program does not work right.
Flaw
The program could work better.
Requested Feature
On someone's wish list.
Pie in the Sky/When Pigs Fly
Unlikely to be implemented (usually because it's out of the scope of the application's purpose).
Legal Requirement
Usually a copyright requirement.
-------------------------------
Status Descriptions:
Fixed, Compile
Bug does not occur in the stated compile number.
Deferred
Problem resolution deferred to a later release.
No Resolution
Problem will most likely never be resolved. This can occur for several reasons; It be to much effort to make a feature work under an old operating system, or it would require patching or bypassing the operating system or see the Bug Type, to name a few.
-------------------------------
Outstanding Resolutions:
0:
1: #28
2: #69, #77
3: #29, #41, #45
4: #1, #10, #11
Bug: #28
Flaw: #29, #41, #45
Requested Feature: #1, #10, #11, #69, #77
Pie in the Sky/When Pigs Fly:
Legal Requirement
-------------------------------
Report Layout
### Bug Number
Priority: See Bug Priority List
Type: See Bug Type List
Compile: Compile number where bug was first reported.
Version: Release version where bug was first reported.
Description: Short description of bug.
Status: Resolution status of the bug report.
-------------------------------
Bug List:
001
Priority: 4
Type: Requested Feature.
Compile: 2
Version: a3
Description:
Allow user to layout the Register grid to their liking.
Status: Deferred
Added the Register Layout menu selection to Functions menu (requires no code). Will be functional in a latter release.
002
Priority: 2
Type: Requested Feature
Compile: 2
Version: a3
Description:
Entry limitation of 50 prevents several features from being tested.
Status: Fixed, 3
Removed the entry limitation. The entry limitation was set to test this feature out before compilation. The entry limitation is for the final release version 1.0.0.
003
Priority: 3
Type: Legal Requirement
Compile: 2
Version: a3
Description:
Copyright notice displayed as 1994. Should be 1995.
Status: Fixed, 3
Changed About Home Accounting window copyright notice to display 1995.
004
Priority: 0
Type: Bug
Compile: 2
Version: a3
Description:
Register window, Edit function view, Add button fails with error message:
The class "object" does not contain the method Add Entry.
Double-clicking an empty row does not create this error, so the bug is related to the Add button only.
Status: Fixed, 4
Error doesn't occur in the interpreter.
Deleted the Window Item Behavior and replaced it with the one used by the Edit button. Recompiled. Bug still occurs.
Deleted the Add button and created a new add button. Recompiled. Bug Fixed.
005
Priority: 1
Type: Bug
Compile: 2
Version: a3
Description:
When translating the a2, 5 entry data base, no entries are made and no accounts are created (cash or budget).
Status: Fixed, 3
Another problem associated with the way the ABC's work vs. HA. The bug was in the Documents Manager class. When the Documents Manager updates it's register (that shows the active data bases), it gets information from the Document Manager associated with the new document. The problem is that the /Get Data method is called. In the ABC's not only does this get the contents of the data attribute but also does an extraction of the data. HA uses the Load persistant to store the extracted data. However the file loading routines also use the Load persistant to store the loaded file data. A new document creates a new manager that contains no data. The extraction process replace the file data with the empty data set.
The Documents Manager now calls HA Documents /Get Document Data method, which just returns the contents of the Data attribute.
006
Priority: 1
Type: Bug
Compile: 2
Version: a3
Description:
Register Entry window. When adding an entry, the setting of the Payment/Deposit for a non-budget entry is ignored. The entry is always made as a payment.
Status: Fixed, 4
The problem is that when you select NONE from the budget account popup menu a local in the method called returns the wrong radio button name. Since the button name is wrong, no button change occurs and the payment/deposit attributes are not modified. The action of selecting NONE defaults to the account type of the initial budget account which most likely is an expense (payment) entry. Once you make an entry everything gets set correctly.
Fixed the name returned by the local. Recompiled. Bug still present.
The default data record created for an add entry function is to have both record attributes (Payment and Deposit) set to 0 dollars. The code determines initial payment/deposit setting by examining the deposit attribute. If the deposit attribute is 0, then the type defaults to payment.
The default data record attribute, payment, now defaults to one penny. When you now make a type selection the code can now detect which type to use. Since you are required to make a valid amount entry (non-zero) to add a record to the data base, the default setting will automatically be replaced before addition occurs.
007
Priority: 1
Type: Flaw
Compile: 2
Version: a3
Description:
Register window, Search function view, Search popup menu should use metacharacters (separator bar).
Status: Fixed, 3
The search popup menu should not have been changed to using the popup menu class that doesn't use metacharacters.
The search popup menu now use the default popup menu class.
008
Priority: 1
Type: Bug
Compile: 2
Version: a3
Description:
Register window, Edit function view, Sort popup menu should show the same data record attributes as the Search popup menu does.
Status: Fixed, 3
The Sort popup menu now uses the same code as the Search popup menu.
009
Priority: 3
Type: Flaw
Compile: 2
Version: a3
Description:
The limit error message header has the text "GeneralNotice:". Need a space between General and Notice.
Status: Fixed, 3
A space character was added between General and Notice.
Since the limit has been removed, this error message will never be seen in the compiled application.
010
Priority: 4
Type: Requested Feature
Compile: 2
Version: a3
Description:
Error Messages large window. The Code scroll list should be right justified.
Status: Deferred
Although you are allowed to chose the justification in the interpreter, the ABC's do not support justification in a list record.
I will create a new Scroll List class in the future that does use text justification.
011
Priority: 4
Type: Requested Feature.
Compile: 2
Version: a3
Description:
Error Messages large window. Add a marker indicating which codes are display enabled.
Status: Deferred
This will be added in a future release.
012
Priority: 1
Type: Bug
Compile: 2
Version: a3
Description:
The Preference window can not be opened or brought in front of the Budget-Monthly window even though the Windows menu shows that it can be done.
Status: Fixed, 3
The Preference window's maximum priority was set below that of the Budget-Monthly window. The minimum priority was correct.
The Preference window's maximum priority is now set to the Budget-Monthly's maximum priority.
013
Priority: 1
Type: Bug
Compile: 2
Version: a3
Description:
If you open the Register window from the Window Bar, then the vertical scroll bar should be active, it isn't.
Status: Fixed, 3
What was happening is the way scroll bars (controls in general behave) are displayed. The Register Scroll Bar doesn't actually belong to the Register View (where it is managed). It is owned by the Register Window. Window items are opened before the window. Most controls require a valid graph port to be set, an active and visible window (or view), in order to be drawn as highlighted (active). Most of HA window and view classes call an update method before they are opened. Since the scroll bar belongs to the window, which isn't active yet, it is set inactive in the control structure when the view sets it's attributes. Since the window doesn't manage the scroll bar it doesn't activate it when it is actually opened. Note: Any view update will cause the scroll bar to be drawn correctly.
By opening the view first and then calling the update view method correct the problem. This creates a valid graph port for the view and thus results in the scroll bar's active attribute being set to active. When the window is finally drawn, the scroll bar is drawn highlighted.
014
Priority: 2
Type: Flaw
Compile: 3
Version: a3
Description:
When a window closes, the data base number of the new front window does not become the current data base. This fact is reflected in the data base manager's window.
Status: Fixed, 4
Modified the Close Window to get the session number of the new front window and set the active session to it. The data base manager's window is then updated.
015
Priority: 1
Type: Bug
Compile: 3
Version: a3
Description:
Register Entry window. The Payment/Deposit buttons are not set correctly for a non-budget account selection when editing an entry from an a2 converted file.
Status: Fixed, 4
In previous versions, a non-budget account selection was stored as "NONE" in the data base. In the a3 version a non-budget account selection is stored as an empty string. HA a3 in most places only recognizes the empty string as a non-budget account entry.
Modified the data base converter to detect "NONE" entries and convert them to empty string entries.
In addition, I removed all old code that looks for a "NONE" budget account entry in the data base.
016
Priority: 1
Type: Bug
Compile: 3
Version: a3
Description:
Interpreter detected bug.
When you close the current data base, the application gets into an infinite loop updating the file menu.
Status: Fixed, 4
My debug code traps this problem (a non-existent data base is referenced as the active session). The compiled app just slows down a little bit which is unnoticeable.
What was happening is that the Documents Manager was updating the active session before the document to be closed was actually closed by the application class. The application class (Home Accounting Application) assumed that the document to close was indicated by the active session.
The application now gets the session number from the document to close.
017
Priority: 3
Type: Flaw
Compile: 3
Version: a3
Description:
Register views; Sort and Search popup menus are not wide enough for the Split Account Number entry.
Status: Fixed, 4
Increased their widths from 160 to 170 pixels.
018
Priority: 4
Type: Requested Feature.
Compile: 3
Version: a3
Description:
Edit menu, Style submenu doesn't have justification selections.
Status: Fixed, 1.0.0a4p2 c1
Added a new class, HA Style Menu. Replaced the Edit menu's standard style class reference to the new style class.
Note: The ABC's Edit Text classes do not make use of justification selections. Therefore, making justification selections from the Edit menu will have no affect on editable text.
This limitation of the ABC's will be fixed by a future text editor class of my own.
019
Priority: 2
Type: Flaw
Compile: 3
Version: a3
Description:
Data Base Manager window's position is not being remembered when closed.
Status: Fixed, 4
When the last data base is closed, the Data Base Manager window is automatically closed. The automatic system closes the window by calling /Close on it's self.
The automatic system now calls /Close Window. This allows the Window Manager to properly record the windows last position.
020
Priority: 2
Type: Flaw
Compile: 4
Version: a3
Description:
When you change colors in the Preference window (Reg Color) and close the Preference window by clicking the OK button. Only the front Register window reflects the new colors. All other open Register windows reflect the new colors settings only when they are redrawn.
Status: Fixed, 5
Window classes that make changes that affect other window settings call the universal method Update Window, which calls the Update Window method for all windows belonging to active session.
All windows now call the Update Windows universal which calls each open windows Update Window method.
021
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
Data Base 2 Register window can not be brought in front of the Data Base 3 DB Preference window.
Status: Fixed, 5
The Window Managers Check Window Priority method was supposed to be modified to check windows based on their session number rather than their name.
Modified the Check Window Priority method to compare window priorities only on windows with the same session number, no session number and application specific windows.
022
Priority: 3
Type: Flaw
Compile: 4
Version: a3
Description:
Preference window, DB Preference window, Address view. After loading a preference file the views are not updated to show the new address names.
Status: Fixed, 5
Modified the Load method to call the universal method, Update All Windows.
023
Priority: 3
Type: Flaw
Compile: 4
Version: a3
Description:
The spinning ball stops spinning for a while after a large data base is loaded just before the Register window displays the data.
Status: Fixed, 5
Once the data is loaded, the data records are updated to reflect the outstanding balances. With large data bases, this requires a lot of processing the more accounts that are referenced in the data base.
Added a cursor update call into the processing loop that calculates the outstanding balance of a data record.
024
Priority: 0
Type: Bug
Compile: 4
Version: a3
Description:
Home Accounting crashes when you print the Preference windows data after loading a preference file.
Status: Fixed, 5
The Set Load Preference method for the Time Selections class was stripping off the version number for the class from the incoming data. The problem is that there is no version number at the record level. Therefore dummy NULL entries were being made for the good data that was stripped off.
Removed the stripping method from the Time Selections classes Set Load Preference method.
025
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
When you select ALL ACCOUNTS in the Budget-Monthly window (budget account popup menu), the December budget entry field is still active.
Status: Fixed, 5
The method setting these fields was calculating the annual budget totals rather than the monthly budget totals. It just so happens that the number of budgets was 11 which resulted in the first 11 entry fields to be made inactive. If there were 12 budget accounts, the bug would not have been seen. If there were more than 12 budget accounts the application would have crashed.
The method to calculated the monthly totals has been fixed.
026
Priority: 2
Type: Flaw
Compile: 4
Version: a3
Description:
If you change a budget's monthly setting in the Budget-Monthly window and then select Cancel, the reset of the monthly setting is not reflected in other open windows until they are updated.
Status: Fixed, 5
When the Budget-Monthly window is closed the universal method, Update All Windows is called.
027
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
Preference window, Reg Color view. When you select a color from the Palette Manager window and return to the Preference window, the sample grid is updated correctly. But if another window is in front of it (like the Statistics window), the sample grid is also drawn in that window to.
Status: Fixed, 5
Another Grid class problem with the active graph port setting.
Before the Reg Color view updates the sample grid, the Preference window is brought forward if it is not the front window. This is a quick fix. I am designing a whole new grid system that will eliminate all my problems with the present grid system.
028
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
If you select the system color wheel to choose a color for the Reg Color view's sample grid the computer locks up. This bug does not occur consistently.
Status: Deferred
What appears to be happening is that HA is running out of memory. In an attempt to release HA's reserve memory a conflict occurs between the Mac's memory manager and CPX's memory manager.
A temporary solution is to not use the color wheel when available HA heap memory gets within 50k bytes of the memory reserve setting of 100k bytes (don't use it below 150k of free memory).
029
Priority: 3
Type: Flaw
Compile: 4
Version: a3
Description:
There are many multiple updates to the front window at times.
Status: Deferred
You get a window update when one window is on top of another window and the top window is moved or closed. The closing of many of HA's windows also causes other windows to be updated. It is impractical to have HA monitor system window updates and to determine if a new update will produce no change in any particular open window and thus should be ignored for that window.
However, until the ICC Manager class is functioning (scheduled for the a4 release), I'm not going to try an fix this annoyance where multiple updates can occur because of the present coding that makes sure windows don't display stall data. I feel multiple updates are better than no updates.
030
Priority: 2
Type: Flaw
Compile: 4
Version: a3
Description:
The text of a help selection is drawn in the save frame rather than the displayed frame. When you edit the text it suddenly redraws it's self to the display frame from the cursor down (not the text before the edit cursor).
Status: Fixed, 5
A very old outstanding bug.
Finally determined what Edit Text class methods to call to get the text drawn (one time) in the current display frame (I have gotten it to redraw before, but it usually occurred more than one time which was just as annoying). I do it by getting the current frame and then setting the current frame to the value of the current frame. Setting the frame causes the right commands to be issued to the Text Editor to get it to redraw the text correctly. In my opinion setting the text and/or it's style record should automatically cause the text to be redrawn in the current frame.
031
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
When multiple Register windows are open and you do anything to cause all of them to be updated, all of them suddenly show the data from the front most Register window.
Status: Fixed, 5
The Update Window methods all assume that they are the front window. Therefore they all ask for the data from the active session.
All update methods (window, view, register etc.) now use the session number of the owning window or document.
032
Priority: 3
Type: Flaw
Compile: 4
Version: a3
Description:
Preference window, Reg Color view, sample register grid when opened does not reflect the current color settings.
Status: Fixed, 5
When the view is opened, a call to redraw the sample grid is called.
033
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
Selecting Revert from the file menu does not revert the data base.
Status: Fixed, 5
The old revert method was designed to work with a single open data base.
The revert system has been modified to install the loaded data into the correct document manager (instead of being ignored).
034
Priority: 1
Type: Requested feature.
Compile: 4
Version: a3
Description:
Need to monitor memory consumption dynamically rather than opening the Statistics window and clicking the update button after every action being tested.
Status: Implemented, 5
Added the Memory Monitor floating window class. This class is incorporated into the core code of the application. In the Preference window, General view you can set how often the window is updated ( 60 tics to 54000 tics).
035
Priority: 1
Type: Bug
Compile: 4
Version: a3
Description:
Even if you set a window to use it's own page set up, it always uses the application's page setup.
Status: Fixed, 5
The Page Setup universal was designed to work with a single data base. It sets the default attributes of a window class to the page setup chosen. This does not work with multiple open data bases.
The P&S Print Record class has been modified to maintain the Page Setup settings for the window class (in a new attribute, Printer) that it manages.
The contents (a <<Printer>> instance) of the Printer attribute is not saved in the preference file.
The Page Setup universal method and the two Print Layout classes (Grid and Text) Print methods have been modified to use the P&S Print Record's page setup information for printing.
036
Priority: 2
Type: Bug
Compile: 5
Version: a3
Description:
The Memory Monitor window shows a 32 byte reduction in available object heap space when HA is idle (no windows open, no data base loaded etc.).
Status: Fixed, 1.0.0a4p1 c1
This is a bug in CPX version 1.0.3 which is supposed to be fixed in version 1.1. Every update of the memory monitor causes an integer conversion which is where the memory loss is occurring.
HA a4 will be ported to CPX version 1.2.2.
037
Priority: 2
Type: Flaw
Compile: 5
Version: a3
Description:
The Help window can not be resized larger than 640 by 480.
Status: Fixed, 7
The following windows now have a maximum size setting of 1600x1600:
Error Messages, Logical Find (future feature), Registration and Budget.
038
Priority: 3
Type: Bug
Compile: 5
Version: a3
Description:
If you launch HA by double-clicking a preference file, the preference data is not loaded and no default data base is created. However the Data Base Manager window is opened with no active data bases displayed.
Status: Fixed, 7
Multipart problem:
Path: Home Accounting Application/Open Documents/load file?/load data file case 1.
Bug 1:
The selected pref file references are stored in the IAC persistant before the data base file references are stored at startup. When the data base file references are stored in the IAC persistant the pref file references are deleted.
Bug 2:
There was no check to see if no data base file references were being loaded from startup. A check is now made. This is why no new data base was being created, the IAC persistant indicated a data base file reference was present, but in reality there was none.
Path: Home Accounting Application/Open Documents/load file?/pref file case 1.
Bug 3:
There was no check to see if no pref file references were being loaded from startup. A check is now made.
039
Priority: 2
Type: Bug
Compile: 5
Version: a3
Description:
When the Register Entry window is first opened, the Post Date and Cleared Date field entries are displayed in the display format rather than the entry format. When the fields are edited they are displayed in the entry format.
Status: Fixed, 6
The Register Entry window's Update Window method uses the HA Data Base Record's Convert Attribute method to translate the record's attributes for display. The problem is that the Post Date and the Cleared Date need to be converted into an Entry format rather than a Display format.
The Post Date and Cleared Date are converted separately from the other attributes by the window's Update Window Method.
040
Priority: 0
Type: Bug
Compile: 5
Version: a3
Description:
If the entry format is set to DDMMMYYYY and you make an entry in the Cleared Date field HA crashes.
Status: Fixed, 6
The Register Entry's Set Cleared Date method calls the Convert Entry Date method which fails. Because there is no failure control on this method HA crashes.
Placed a failure control on the Convert Entry Date call which causes the users entry not to be store in the data base record if a failure occurs.
Note: The failure should not have occurred to begin with. See bug report #42.
041
Priority: 3
Type: Flaw
Compile: 5
Version: a3
Description:
If you create an invalid entry in a date field in the Register Entry window, the error message does not indicate which date field it is referring to.
Status: Deferred
Error management on the date entry routines are handled in the date filter system and not by the window. The date filter system has no way of knowing where the fault came from. This problem will take time to resolve.
042
Priority: 1
Type: Bug
Compile: 5
Version: a3
Description:
The entry format DDMMMYYYY requires the month to be integer?
Status: Fixed, 6
This is related to bug # 040.
Path: DB Convert Entry Date/strip date/check ranges/check month, case 2.
The case should be checking the length of the month entry to 3 not the month it's self. This will always fail, which goes to the next case which looks for an integer value for the month, which always fails.
Measures the length of the month entry and compares it to 3.
043
Priority: 1
Type: Bug
Compile: 5
Version: a3
Description:
If you double-clicking a preference file while HA is running the following error message appears:
The class "File" does not contain the method "Close".
You are returned to the Finder.
Status: Fixed, 6
Path: Home Accounting Application/Open Documents/load file? /pref file case 2/load pref file.
Normal path for opening file is through the File menu which resolves file aliases and store the results in the <<Object File>> instance of a new <<HA Document>> instance. Loading from the Preferences window uses the <<Object File>> instance of the Preferences window which is also used at startup by the default system.
However, Apple Events for loading the a file from the Finder while HA is running is handle by the pref file local described in the path above. This local receives the file reference in a <<File>> instance which is an abstract class an is not designed to actually be used for managing files.
The file specification is extracted form the incoming <<File>> instance. A copy of the <<Object File>> instance from the Preferences window class is created and it's file specification is set to the file specification of the <<File>> instance. The normal loading of a preference file occurs after this.
044
Priority: 1
Type: Bug
Compile: 6
Version: a3
Description:
Preferences window, Date view. If you select an Entry Format of DDMMMYYYY, the displayed dates in the Register window are shown as MM/DD/YYYY, where the MM is the first two characters of the month after an add or edit.
Status: Fixed, 7
The DB to Display Date universal was using the selected format to create the format of the date stored in the data base record. This bug was not see until a format other than the default MMDDYYYY was selected. The default format (reversed) is the format of the date stored in a data base record.
The universal now always uses the internal format for creating date entries to be stored in a data base record.
045
Priority: 3
Type: Flaw
Compile: 6
Version: a3
Description:
You can enter a date in the Post Date or Cleared Date fields that does not meet the Entry Date format but is a valid date. The date is accepted, then converted to the entry date format.
Status: Deferred
Another contention problem between the Date filter class and the Register Entry class on how to handle different date formats.
The date filter class accepts a numeric entry for the month even though the selected entry format specifies a text month entry.
046
Priority: 1
Type: Bug
Compile: 6
Version: a3
Description:
If you launch HA by double-clicking a preference file, the following error message appears:
The class "File" does not contain the method "Open".
You are returned to the Finder.
Status: Fixed, 7
Path: Startup Application/set default preference file case 1.
Preference file loading from startup are stored in the IAC persistant and deferred until the end of the startup sequence. The preference file references are stored as <<File>> instances in the IAC persistant which is an abstract class an is not designed to actually be used for managing files.
At the end of the startup sequence, the IAC persistant is checked to see if the user had selected a preference file to load at startup. If the flag in the IAC persistant is set TRUE, then the <<File>> instance is extracted and sent to the loading routine. If the flag is set FALSE, then the default preference system is called.
The file specification is extracted form the stored <<File>> instance. A copy of the <<Object File>> instance from the Preferences window class is created and it's file specification is set to the file specification of the <<File>> instance. The normal loading of a preference file occurs after this.
047
Priority: 1
Type: Bug
Compile: 7
Version: a3f1
Description:
The positions of the DB Preferences and Preferences windows are not remembered when use close the windows from the file menu close window selection, using command W, clicking the close box or clicking the cancel button. However, their position is remembered if you click the OK button.
Status: Fixed, 8
The last modification to the Preferences class was to unify all the ways closing the Preferences window (DB Preferences is a subclass of Preferences) handles a cancel action. All cancel actions are filtered through the Preferences/Close Window method (the close box uses go away, the cancel button uses cancel, the file menu uses close window). This method calls the Window Manager/Close Window method which validates the closing of the window (any changes?). If there are no changes or the user discards the changes, then the window's position is updated. Then the Window Manager calls the windows Close method. The Preferences/Close method restores the previous preferences.
The OK method replaces the previous preferences with the current preferences which causes the current preferences to be kept when the Preferences/Close method is called.
The problem is that the previous preferences contain the window positions of all windows closed before the opening of the Preferences window, but not after it is opened (information about windows is managed by the Windows Info Manager). So when you cancel the Preferences window all window positions after the Preferences window is opened are discarded.
This bug required two modifications:
Separate the OK method so it calls the Window Manager/Close Window method directly thus bypassing what the Preferences/Close Window method does.
In the Preferences/Close Window method, the Window Info Manager of the current preferences is replaced by the Window Info Manager of the previous preferences. Now when the Close method restores the previous preferences, the window position information of the current preferences are kept.
048
Priority: 1
Type: Bug
Compile: 8
Version: a3f1
Description:
If you load a preference file with address records and then load another preference file with the same address records, you get an address book with double entries.
Status: Fixed, 9
The Address Book Manager was not initializing the address book data base before addding the new entries.
049
Priority: 1
Type: Bug
Compile: 8
Version: a3f1
Description:
If you change any reserved error code number to any valid code number, you can delete it.
Status: Fixed, 9
The Update Code method now check both the before and after error code numbers.
050
Priority: 1
Type: Bug
Compile: 9
Version: a3f2
Description:
In the search view of the register window, you can not select anything but ALL from the popup-menu.
Status: Fixed, 10
Update View method in the HA Search View has a local to find the session number of the owning window (register). The method had no code.
051
Priority: 1
Type: Bug
Compile: 9
Version: a3f2
Description:
Selecting the security level for the data base to data file and memory, only entries created after making changes are actually encrypted.
Status: Fixed, 10
At present the security features are for test purposes only. Technically you should not be allowed to change this setting without a password (which is used as a part of the encryption/decryption key). At the moment the code doesn't need a password to check things out (which is why it's not secure). However, I have modified the preference system to encrypt/decrypt on passed on the setting in the view (it does not happen automatically because of the time to process a large data base).
052
Priority: 2
Type: Bug
Compile: 9
Version: a3f2
Description:
Setting either the Display or Report status for any of the applications error codes in the error preferences causes an error message to be generated about changing these codes.
Status: Fixed, 10
The update routine was only looking at the error code number being changed. If the error code was reserved for Home Accounting, then the a warning message is generated.
In new routine fixed routine, if your not changing the code or type, then you are allowed to update the error code (a status change is assumed).
053
Priority: 0
Type: Bug
Compile: 9
Version: a3f2
Description:
Working with the data base encrypted, caused the program to crash when a register entry was moved from one entry position to another.
Status: Fixed, 10
The encrypted record class was not trapping the insert record method call in the data record class. This led to double-encryption of the record. Data contained in an encrypted record can not be extracted from a double-encrypted record.
Added an insert record method to the encrypted record class which prevents double-encryption of a data record.
054
Priority: 0
Type: Bug
Compile: 9
Version: a3f2
Description:
Working with the data base encrypted, caused the program to crash when reconciling an entry.
Status: Fixed, 10
The encrypted record class was not trapping the get budget type method call in the data record class. The generic get budget type method can not handle an encrypted record.
Added a get budget type method to the encrypted record class.
055
Priority: 2
Type: Flaw
Compile: 9
Version: a3f2
Description:
When the palette Manager window is open, there are several menu selections enabled, but do noting when selected.
Status: Fixed, 10
The Palette Manager is not an intergal part of Home Accounting, but is an attached feature. Therefore, the palette manager window is not managed by Home Accountings window manager. The Home Accounting Application class uses the window manager to determine which application features to enable in the menu bar.
The Update Menus method in the Home Accounting Application class now checks the front window. If the front window is the palette manager window, then no application menu features are enabled.
056
Priority: 2
Type: Flaw
Compile: 10
Version: a3f3
Description:
There is a 4 pixel gap between the help view and the grow box.
Status: Fixed, a4p1 c1
The view and it's scroll bar vertical sizes were a little off.
057
Priority: 2
Type: Flaw
Compile: 10
Version: a3f3
Description:
In the register entry window if you select a budget account of none, then select another budget account, then the budget type buttons are not updated properly.
Status: Fixed, a4p1 c1
The old account type was being passed to the update routine.
058
Priority: 1
Type: Bug
Compile: 10
Version: a3f3
Description:
In the DB Preferences window, changing the account type (income or expense) does not update the entries in the data base.
Status: Fxed, a4p1 c1
Added code to the Set Type method to process the data base for a change in the budget account's type.
059
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
Making a change in a monthly budget entry in the Budget-Monthly window is not permanent if you select another account.
Status: Fixed, a4p2 c2
A temporary fix is to tab out of the field before selecting another account.
060
Priority: 0
Type: Bug
Compile: 1
Version: a4p1
Description:
In the DB Preferences window, Accounts preferences, adding a new account that gets inserted at the beginning of the list causes a type 1 error to occur.
Status: Fixed, a4p2 c2
A change in the API of CPX 1.2's insert-nth primitive. An index value of 0 is no longer allowed.
The insertion routine to insert a new account name in the scroll list uses a default index value of 0. This has been changed to 1. If no insertion point is found (based on an alphabetical search), then the default index value is used.
061
Priority: 0
Type: Bug
Compile: 1
Version: a4p1
Description:
DB Preference window still open for a data base you have closed.
Sequence of events:
DB Preferences window is open and you have made changes.
You click close on the data base with it's DB Preferences window still open.
The dialog box asks if you want to discard your changes (for the DB Preferences) and you click no.
The DB Preferences window stays open.
The Register window closes.
A dialog box asks if you want to save your data base (preferences are flagged as changed).
Click the save button.
Enter a file name.
Click the save button.
Home Accounting locks up.
Status: Fixed, a4p2 c2
Clicking the no button to prevent the DB Preferences changes from being discarded should have canceled the closing of the data base.
062
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The account names in the Budget-Monthly window should be shown alphabetically.
Status: Fixed, a4p2 c2
Just an oversight.
063
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The random function of the calculator always returns 0 if either entry is not an integer value.
Status: Fixed, a4p2 c2
Real values are now rounded to integers.
064
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
Add the calculator feature that computes the average value of the two entries.
Status: Added, a4p2 c2
065
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
If the totalize function is not enabled, then the copy function should copy the result.
Status: Modified, a4p2 c2
066
Priority: 0
Type: Bug
Compile: 1
Version: a4p1
Description:
If the DB Preferences window is open and you make changes to the budget accounts, then open the Budget-Monthly window and make changes to the same accounts, then switch back to the DB Preferences window make some more changes to those account, switch back to the Budget-Monthly window and click the cancel button, all changes made to the budget account from the opening of the Budget-Monthly window to it's closing go away (even those in the DB Preferences window).
Status: Fixed, a4p2 c2
Both preference windows make copies of the preferences that they affect when they open. When you click cancel the original preferences are restored to the point the window was opened. Since all preference editors work on the active preferences any cancelation in any preference editor window will affect all other preference editor windows.
The fix will was to give the Budget-Monthly window higher priority than the DB Preferences window. This will force the user to decide whether to keep their changes or discard them before switching to another preference editor.
067
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the DB Preferences window, it would be nice if the annual budgets and starting balances were visible in a scrolling window alongside their associated account.
Status: Modified, a4p2 c2
The Cash Accounts and Budget Accounts are now in separate preference views. A new general purpose class, Prefs Grid View, now simulates a multiple column scroll list. With the separated preference views, there is now enough room to use it. The usuage count has been added in a third column.
068
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Preferences window, add some kind of indicator as to which scroll list (Cash or Budget) will be affected by clicking on a button.
Status: Fixed, a4p2 c2
The changes for bug report 68 resolved this report.
069
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Calculator window, have the math keys select the math function to perform (+ does an addition).
Status: Deferred
The calculator has to be completely redesigned to impliment this request, because the edit text fields intercept the the + and - keys which are valid entries for a number.
070
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Preferences window, when you click the Save button, make the default file name the name of the application's preference file.
Status: Modified, a4p2 c2
071
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
Eliminate the NONE (non-budget entry option). Place all entries under the budget management system. This will allow $0 entries (to show torn up checks) into the register entry window.
Status: Modified, a4p2 c2
Since Home Accounting identifies a non-budgeted entry as an income or expense by which field has a 0 entry (payment or deposit) you can not make a $0 entry.
By elimination of the NONE selection and moving all entries under the budget manager, the code is greatly simplified and allows a $0 entry. The information about income or expense is stored in the budget account record, which the non-budgeted account did not have. The converter has been modified to create a new budget account called, Non-Budgeted Expense or Non-Budgeted Income (if they don't already exist) when converting older record entries.
072
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Register Entry window, if the field is left blank, then default to a 0 (zero) value rather than an error message.
Status: Fixed, a4p2 c2
This was a modification to the Check Entry Filter.
073
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the DB Preferences window, Addresses view, let the Set button be the default button.
Status: Modified, a4p2 c2
Since the Cancel button of the main view is already flagged as the default window item (the object that responds to the Return key), no other window item can be flagged as the default window item.
The modification was to make the enter and return keys execute the set button's code. Exiting the edit field (by selecting one of the other targetable window items such as the scroll lists) does not execute the set buttons code. This means that to set the selected budget accounts creditor attribute, you need to press the tab, return or enter key or click the set button.
074
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
Allow the Enter and Return keys to work in all editable fields where there is no default button.
Status: Modified, a4p2 c2
This required the creation of the Special Keys subclass (HA Special Keys). Not all edit text fields use my HA Special Keys enhancement.
075
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the DB Preferences window, Addresses view, add an update button that updates all data base entries (name field) to the name of the creditor of the selected budget account.
Status: Added, a4p2 c2
076
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Preferences window, General view, add an auto window update check box which will set the default setting of the Window Update button in the Register Entry window.
Status: Added and modified, a4p2 c2
This change modifies the Home Accounting Preferences file. The preferences converter has also been modified to add the new preference to older files as they are loaded.
077
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
If a file is loaded that has been corrupted, Home Accounting will crash at unexpected times. Verify the validity of the file before loading it.
Status: Deferred
This is an ongoing problem in all applications. For speed purposes HA doesn't do extensive verification of the validity of a file that it loads. In the beta series this will be corrected. Basically every component of each record will need to be verified against the preference structures. The fall outs will be stored in a recovery buffer that you will be able to edit and reload accordingly.
078
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
In the Calculator window add the ability to set the rounding of the result.
Status: Added, a4p2 c2
079
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
In the Address Book window the order of the Contact, Phone and Type fields is confusing. Suggest you change the Order to; Phone, Type and Contact.
Status: Modified, a4p2 c2
The phone number is associated with the record not the contact.
080
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
In the Register Entry window , the Add button should be dimmed if there has been no changes made in the record. If you answer the phone while making entries, it can be confusing when you come back and can't remember whether you added the current record or not.
Status: Modified, a4p2 c2
You need to change the contents of a field to enable the add button.
081
Priority: 2
Type: Bug
Compile: 1
Version: a4p1
Description:
In the Budget-Monthly window, Expense Budget Account grid Actuals column shows negative values?
Status: Fixed, a4p2 c2
With expences the deposit value must be subtracted from the payment value to get the actual value. This bug was created in the process of coping the code from the income routines.
082
Priority: 2
Type: Requested Feature
Compile: 1
Version: a4p1
Description:
Add a year reference on the printouts for the Budget, Budget-Monthly and Register windows.
Status: Added, a4p2 c2
A the bottom of the printed page to the right of the date, the year of the data base that the data relates to is shown.
083
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
The Style submenu doesn't appear?
Status: Fixed, a4p2 c2
Some how the menu behaviors again were trashed.
084
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
The Font menu stuff is not always enabled?
Status: Fixed, a4p2 c2
The enabling of these items is now handled by the application class, rather than individual windows.
085
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The About Home Accounting window should be closeable by pressing any key on the keyboard.
Status: Fixed, a4p2 c2
086
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
Many windows contain no editable text fields but do contain one or more buttons. It would be nice if you can select a button by pressing the key for the first character of the button's name.
Status: Modified, a4p2 c2
I created a new general purpose class, Verify, to replace the answer primitive that manages these kinds of windows. However, not all windows are created by Home Accounting's code. Some windows are created and managed by the ABC's. I have attempted to override as many of these that you will encounter during general use as I could.
087
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
When saving a file, many times the default name includes a colon. This is an invalid character for a file or volume name.
Status: Modified, a4p2 c2
The default file name was derived from the windows title which includes the colon to identify the data base number. The new routine attaches the data base number after the year separated by a period.
088
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
If you open a file that is locked and then try to save the file you get a file error in a modal dialog box. A file is created with no data?
Status: Modified, a4p2 c2
This bug was introduced when PI changed the API for CPX 1.2 for loading object files. I now override the Open method and force the Read Only? attribute to FALSE.
The file that is created contains a resource for. The resource fork is created before the data fork by my code which ignores the Read Only? attribute setting.
089
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
When editing a entry in the register when no entries are displayed. A double-click on a blank entry opens the register entry window in edit mode with an entry not displayed. Do the following:
Open the register window.
Select the display view.
Select a cash account not referenced in the data base.
Double-click a blank entry.
Status: Modified, a4p2 c2
This is because of to old code from the a2 series. The routine to determine what entry to select in a data base when a click occurs in the register should return a zero (0) reference. In the a2 series if there was no display list or the top entry wasn't displayed, then the routine created a linear index from the top entry to the selected row. In the following versions (a3 and on) the data base system was managed by a manager (in a3 the view, a4 by a data base manager). Linear indexing can no longer be used as a way of determining what data base entry to edit.
The fix was to have the code return a zero (0) reference when there is no display list or the top entry is not displayed. This forces the edit routine to call the add routine.
090
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The total rows in the budget window are a little off.
Status: Fixed, a4p2 c2
091
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The check column (cleared entry) is not centered.
Status: Fixed, a4p2 c2
092
Priority: 2
Type: Flaw
Compile: 1
Version: a4p1
Description:
The account popup menus are not wide enough in the register views, display and reconcile, the windows register entry, reconcile and budget-monthly for the name sizes allowed in the preference windows.
Status: Fixed, a4p2 c2
093
Priority: 2
Type: Bug
Compile: 1
Version: a4p1
Description:
The registration window keeps the changes, even when you select cancel.
Status: Fixed, a4p2 c2
094
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
The data printed in the budget account and type fields for the register window are reversed.
Status: Fixed, a4p2 c2
Another insert-nth problem (see report #60). This appears to be the last used insert-nth primitive.
095
Priority: 1
Type: Bug
Compile: 1
Version: a4p1
Description:
You can not enter negative dollar amounts in the deposit field of the register entry window. This is need to add reconcilation correction entries.
Status: Fixed, a4p2 c2
The Make Integer universal, Dollar Filter class and Set Deposit Value method have been modified to accept negative dollar values. The Dollar Filter and Dollar Filter-Extra classes have been modified to allow enabling/disabling the acceptance of negative dollar entries.
Negative dollar values are allowed only in the Register Entry and Reconcile Entry windows.
096
Priority: 1
Type: Bug
Compile: 2
Version: a4p2
Description:
If the Budget-Monthly window is the front window, the Windows menu indicates that the Preferences window can be opened or brought to the front. Selecting Preferences does nothing.
Status: Fixed, a4p3 c3
The changes that occured because of bug report #66 created this problem.
The Preferences window's maximum priority should have also been set to the new maximum priority of the Budget-Monthly window.
The Windows menu items are enabled by the Home Accounting Application class, which recognizes the differences between data base windows and application windows. Opening a window is handled by the Window Manager class which only looks at the priority of the requested window relative to the priority of the open windows indifferent to who they belong too.
097
Priority: 2
Type: Bug
Compile: 2
Version: a4p2
Description:
Holding the mouse button down on either scroll bar arrow button in the DB Preferences views Cash or Budget doesn't update the scroll list until you release the mouse button.
Status: Fixed, a4p3 c3
Event processing was being disabled by the scroll bar's tight execution loop.
My clear events routine now forces update events to be processed when the scroll list is changed.
098
Priority: 2
Type: Bug
Compile: 2
Version: a4p2
Description:
Holding the mouse button down on any of the color controls in the palette manager doesn't do anything until you release the mouse button. They should behave as any other control.
Status: Fixed, a4p3 c3
The Graphic Item class is not designed to do this, since it isn't really a control (it just simulates a button action on a graphic item such as a picture or static text).
I have created a new subclass of Graphic Item, Auto Button, that makes a graphic item act like a real control.
The graphic item's click behavior is executed while the mouse button is down and on the auto button. When the mouse down event occurs, a .5 second auto delay task is posted. When the delay times out the click behavior is posted. A repeat delay is then posted to execute the auto button's click behavior every .1 seconds.
However the event loop process of the ABCs does not support this action so I created an event loop processor within the control loop of the auto button that forces processing of the auto delay and auto repeat tasks during null events as well as window update events so the changes will be made visible.
099
Priority: 2
Type: Bug
Compile: 2
Version: a4p2
Description:
If you enter more than 2 digits to the right of the decimal point in any of the color entry fields (saturation and such) you get an error message about the number places to the right of a dollar entry.
Status: Fixed, a4p3 c3
The percentage filter was created after the dollar filter. Therefore it inherited a lot of the code from the dollar filter (since they both deal with fractions). This was one message that was missed.
100
Priority: 0
Type: Bug
Compile: 2
Version: a4p2
Description:
If you enter more than 2 digits to the right of the decimal point in any of the color entry fields (saturation and such) you get an error message about the number places to the right of a dollar entry and then the program crashes.
Status: Fixed, a4p3 c3
Left off a failure control on the part of the percentage filter that handles this error condition.
101
Priority: 0
Type: Bug
Compile: 2
Version: a4p2
Description:
If you load a preference file that creates an error message, the application crashes when the error messages window opens.
Status: Fixed, a4p3 c3
The debug code routines validate every request and setting of instance attributes. The general purpose local, validate attribute expects the default type for an attribute stays consistent for all data records.
The problem is that the error messages when maintains two different size and location record. To manage this, the Window Info Record allows the Location and Size attributes to be either a point or list of points.
I converted the local, validate attribute, to a class method, Validate Attribute?. This method is then overshadowed in the Window Info Record to check the content of the data to place in the location and size attributes. If the data is a list, then the items of the list are checked.
102
Priority: 2
Type: Bug
Compile: 2
Version: a4p2
Description:
No matter how you select page setup, all windows default to the applications page setup.
Status: Fixed, a4p3 c3
A local in the Page Setup universal method was testing the print record's printer structure of the selected window for NULL (non-existent, the default setting). Which causes the application's page setup and printer structure to be used.
The local now tests for a valid print record. If the print record has no printer structure, then a new printer structure is created for the print record. This also applies to setting the application's page setup.
Also see bug report 104.
103
Priority: 0
Type: Bug
Compile: 2
Version: a4p2
Description:
If you cancel closing the last data base, the reference still appears in the data base manager window, but if you try to select it the application crashes.
Status: Fixed, a4p3 c3
The problem is, that after canceling the close the session reference is not restored. Which means the application no longer could select a document by that session number in some code but did in others. This led to an invalid reference which caused Home Accounting to crash.
If the HA Document/Close method fails, then the session number of the document is reinserted into the active sessions list. The current session is then restored to the first session in the active sessions list (which might not be the one being closed). Also the Window Manager/Close Window method has been modified to handle closing a window under this condition in regard to the current session number.
This also led to fixing the Verify window in regard to calling the proper Window Manager methods when opening (/Open Window) and closing (/Close Window). The previous method were /Open and /Close, which were methods belonging to the Window class. The Verify window class was originally a subclass of Window.
104
Priority: 2
Type: Flaw
Compile: 2
Version: a4p2
Description:
When will Home Accounting support printing from the Finder?
Status: Updated, a4p3 c3
The print engine is a primitive design. To overcome the limitations the Save As Text routines were written to allow better printouts by real word processors.
Home Accounting now implements the 'pdoc' Apple Event for both launching and while running. This was done by adding an IAC Manager class that took over all IAC management functions that used to be handled by individual routines throughout Home Accounting's class system.
The data base, preferences and printing system have all been modified to work with the new IAC Manager. All the modifications did uncover various minor bugs (mostly in printer selection), which have been corrected.
105
Priority: 1
Type: Flaw
Compile: 3
Version: a4p3
Description:
In any of the account preferences views, entering a name like Sav and clicking the Add button produces a beep.
Status: Fixed, a4p3f1
The search routines to determine a valid account name is using an approximation algorithm and is matching Sav to the Savings entry.
The search routines have been updated to allow either an exact or approximate match to be done. The preferences views now look for an exact match.
106
Priority: 1
Type: Flaw
Compile: 3
Version: a4p3
Description:
In any of the account preferences views, entering a name like Sav and clicking the Find button produces a beep.
Status: Fixed, a4p3f1
See bug #105 for the change that created this bug.
The Find routines now use an approximation algorithm in searching for an account name. To add more flexibility I added a find Again button to continue a find search after the current selection.
107
Priority: 0
Type: Bug
Compile: 3
Version: a4p3
Description:
Double-clicking on a data base file launches Home Accounting, but the data base is not loaded. You also get the error message:
12/29/1995 16:46:19
Error
Data Record/Set Entry::
Attribute: [
Value: ( TRUE ( <<File>> ) )
Status: Fixed, a4p3f1
The inputs to the Set Entry method call should have been annotated as lists. This fault can not be checked in the interpreter because there is no real application present to receive the launch and open doc apple events which is the only place this code is executed.
108
Priority: 1
Type: Bug
Compile: 3
Version: a4p3
Description:
Printing the data in any window results in a printout that has only the footer (page number, date etc.) printed.
Status: Fixed, a4p3f1
Extracting all Mac specific code from Home Accounting caused an error to be introduced into one call to the SubPt (subtract point) toolbox method (the inputs were reversed).
109
Priority: 1
Type: Bug
Compile: 3
Version: a4p3
Description:
The text in a text file of the data in the Register window created with the Save As Text function has the balance in the comment field and a 0 in the cash account field.
Status: Fixed, a4p3f1
I added another field to the data base record structure called, Taxable? (always FALSE which is numerically 0). The Save As Text function has not been update to access the data base by attribute yet, so the new field missed ordered the results from the class converter method. The Taxable? value was taken as the cash account. The cash account was dumped as the split record number. The balance was taken as the comment field. The Save As Text function is expected to be updated in the next release.
110
Priority: 2
Type: Bug
Compile: 3
Version: a4p3
Description:
The File menu selection, Page Setup, is never enabled.
Status: Fixed, a4p3f1
Moved management of the Save As Text, Page Setup and Print menu selections from the window classes to the application class. However, the code to enable the Page Setup menu selection was incomplete. Only when there was no open windows did it become enabled.
